Looks like yarl is not yet python 3.11 compatible, maybe worth opening an issue there

Edit: Sorry, didnt see it was a draft

Edit: Sorry, didnt see it was a draft

Lol its fine, fun fact it automatically requested a review from you cause you're also a code owner of the stuff this is changing so I couldn't avoid that (well I might've been able to if I opened this as draft but it was opened as a normal PR to make sure that the actions actually run on it).

maybe worth opening an issue there

And will do

Waiting on warner/python-ed25519#16

We might have to setup a fork for python-ed25519, as it doesn't look like the PR is getting merged any time soon unfortunately

ed25519 dependency removed by #986, unblocking this pr and hopefully can be merged after a rebase

For some context on the tests breaking, this is due to aiohttp and yarl not using the latest cython version, which fixes those bugs. We will have to wait for the next release then

Relevant PRs: aio-libs/aiohttp#6396 and aio-libs/yarl#654

For some context on the tests breaking, this is due to aiohttp and yarl not using the latest cython version, which fixes those bugs. We will have to wait for the next release then

Relevant PRs: aio-libs/aiohttp#6396 and aio-libs/yarl#654

I'm aware, I'm just messing around with stuff to see if i can get it to run in the pipelines by just installing from source to see if anything does break cause i'm bored (but this has turned into too much effort so given up on the idea)

I'm aware, I'm just messing around with stuff to see if i can get it to run in the pipelines by just installing from source to see if anything does break cause i'm bored (but this has turned into too much effort so given up on the idea)

Was just leaving it for prosperity and anybody that stumbles upon this :P

Python 3.11.0b4 is now available, and
Python.org strongly encourage maintainers of third-party Python projects to test with 3.11 during the beta phase and report issues found to the Python bug tracker as soon as possible

Maybe it is irrelevant for this project idk

Python 3.11.0b4 is now available, and
Python.org strongly encourage maintainers of third-party Python projects to test with 3.11 during the beta phase and report issues found to the Python bug tracker as soon as possible

Maybe it is irrelevant for this project idk

We have been trying to test CPython 3.11 for some time now (reason for this pr), but the dependencies of hikari don't support 3.11 yet, so we can't yet as it fails to build

Aiohttp 3.8.3 just released and it has full support for Python 3.11.

We can bump aiohttp to that minimum version and then (hopefully) this pr can be merged with python 3.11 support!

Just re-triggering CI

cchardet was dropped as a speedup for aiohttp (< python 3.10) in this version too due to it being unmaintained.

There have been talks about a replacement, but no outcome yet. Best bet would be to just install aiohttp[speedups]~=same version as requirements to prevent this from happening in the future.

The links for speedups should also have to be updated to just point to the aiohttp docs to see what packages are being installed on top